Skip to contentSkip to conversation

File in append recipe not installed

DISCUSSION p_j_r_m 3 participants 7 messages Mar 12, 2015 – Mar 14, 2015

lore
Share & tools
lore

p_j_r_m

author
#0 lore raw

Hello

I'd like to add an append recipe for base-files in order to install a custom fstab.

In my system I already have this base-files recipes:

    layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files

├── base-files_3.0.14.bbappend
└── files
    └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

do_install_append() {
        echo "======= ${PN}-${PV} INSTALLING fstab ========" install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir} }

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when I build the recipe with bitbake base-files it never gets called and my fstab file is not installed. If the original recipe is base-files_3.0.14.bb, why append is base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i name and put FILESEXTRAPATHS

#1 lore raw
Quoted 22 lines · p_j_r_m

Hello

I'd like to add an append recipe for base-files in order to install a custom fstab.

In my system I already have this base-files recipes:

     layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb
     layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files

├── base-files_3.0.14.bbappend
└── files
     └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

Quoted 7 lines
do_install_append() {
         echo "======= ${PN}-${PV} INSTALLING fstab ========"
         install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir}
}

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when I build the recipe with bitbake base-files it never gets called and my fstab file is not installed. If the original recipe is base-files_3.0.14.bb, why append is base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i name and put FILESEXTRAPATHS

Instead of putting your fstab in 'files', put it in a directory called 'base-files-3.0.14' which is where your FILESEXTRAPATHS is looking.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
author
#2 lore raw

I've tested it, but the problem is the same.My bbappend recipe is not even called ,so it does not matter what i put in it. Why is not called?

El Jueves 12 de marzo de 2015 22:06, Gary Thomas <[email protected]> escribió:

Quoted 22 lines · p_j_r_m

Hello

I'd like to add an append recipe for base-files in order to install a custom fstab.

In my system I already have this base-files recipes:

      layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files

├── base-files_3.0.14.bbappend
└── files
      └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

Quoted 7 lines

do_install_append() {
          echo "======= ${PN}-${PV} INSTALLING fstab ========" install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir} }

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when I build the recipe with bitbake base-files it never gets called and my fstab file is not installed. If the original recipe is base-files_3.0.14.bb, why append is base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i name and put FILESEXTRAPATHS

Instead of putting your fstab in 'files', put it in a directory called 'base-files-3.0.14' which is where your FILESEXTRAPATHS is looking.

Signature · 9 lines
------------------------------------------------------------
Gary Thomas                |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
-- 
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
#3 lore raw
Quoted 2 lines · p_j_r_m

I've tested it, but the problem is the same.
My bbappend recipe is not even called ,so it does not matter what i put in it. Why is not called?

Please don't top-post :-(

How do you know that your bbappend isn't being used/called? If you name it incorrectly, e.g. base-files_3.0.99.bbappend, you should get an error telling you that there is no base-files_3.0.99.bb which matches. Hence if it's named base-files_3.0.14.bbappend and you get no error, it *is* being used.

Please show exactly what is now in your layer (as below). It's really easy to make a mistake with a '_' instead of '-'.

Quoted 55 lines · Gary Thomas
Quoted 22 lines · p_j_r_m

Hello

I'd like to add an append recipe for base-files in order to install a custom fstab.

In my system I already have this base-files recipes:

     layers/openembedded-core-1.4/meta/recipes-core/base-files/base-files_3.0.14.bb
     layers/meta-montavista-1.4/recipes-core/base-files/base-files_3.0.14.bbappend

So I in my layer I have:

layers/meta-mylayer/recipes/base-files

├── base-files_3.0.14.bbappend
└── files
     └── fstab

and I add this base-files_3.0.14.bbappend content:

FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"

SRC_URI_append = "file://fstab"

Quoted 7 lines
do_install_append() {
         echo "======= ${PN}-${PV} INSTALLING fstab ========"
         install -m 644 ${WORKDIR}/fstab ${D}${sysconfdir}
}

but no matter how I put FILESEXTRAPATHS_prepend or how I name my bbappend when I build the recipe with bitbake base-files it never gets called and my fstab file is not installed. If the original recipe is base-files_3.0.14.bb, why append is base-files_3.0.14.bbappend instead of base-files_3.bbappend only? How should i name and put FILESEXTRAPATHS

Instead of putting your fstab in 'files', put it in a directory called 'base-files-3.0.14' which is where your FILESEXTRAPATHS is looking.

--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
[email protected] <mailto:[email protected]>
https://lists.yoctoproject.org/listinfo/yocto

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#4 lore raw
Quoted 7 lines · On Thursday 12 March 2015 18:01:16 Gary Thomas wrote:
Quoted 3 lines · p_j_r_m

I've tested it, but the problem is the same.
My bbappend recipe is not even called ,so it does not matter what i put in it. Why is not called?

Please don't top-post :-(

Quoted 8 lines

How do you know that your bbappend isn't being used/called? If you name it incorrectly, e.g. base-files_3.0.99.bbappend, you should get an error telling you that there is no base-files_3.0.99.bb which matches. Hence if it's named base-files_3.0.14.bbappend and you get no error, it *is* being used.

Please show exactly what is now in your layer (as below). It's really easy to make a mistake with a '_' instead of '-'.

Also, one way to tell for sure whether it is being parsed is to use:

bitbake-layers show-appends

If it's not listed there, check that the layer shows up in:

bitbake-layers show-layers

If the layer doesn't show there, check if it has been correctly added to bblayers.conf. If it is, check that your layer.conf is setting BBFILES such that bbappends in the directory you placed the bbappend in will be picked up.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
author
#5 lore raw

Thanks for your suggestionsThe problem was that my recipe files were taken from sstate directories, even when they were previously cleaned with bitbake -c clean. If I use -c cleansstate instead, all is ok .

El Viernes 13 de marzo de 2015 9:17, Paul Eggleton <[email protected]> escribió:

Quoted 7 lines · On Thursday 12 March 2015 18:01:16 Gary Thomas wrote:
Quoted 3 lines · p_j_r_m

I've tested it, but the problem is the same.
My bbappend recipe is not even called ,so it does not matter what i put in it. Why is not called?

Please don't top-post :-(

Quoted 8 lines

How do you know that your bbappend isn't being used/called?  If you name it incorrectly, e.g. base-files_3.0.99.bbappend, you should get an error telling you that there is no base-files_3.0.99.bb which matches.  Hence if it's named base-files_3.0.14.bbappend and you get no error, it *is* being used.

Please show exactly what is now in your layer (as below).  It's really easy to make a mistake with a '_' instead of '-'.

Also, one way to tell for sure whether it is being parsed is to use:

  bitbake-layers show-appends

If it's not listed there, check that the layer shows up in:

  bitbake-layers show-layers

If the layer doesn't show there, check if it has been correctly added to bblayers.conf. If it is, check that your layer.conf is setting BBFILES such that bbappends in the directory you placed the bbappend in will be picked up.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre
#6 lore raw
Quoted 3 lines · On Friday 13 March 2015 23:16:30 p_j_r_m wrote:

Thanks for your suggestionsThe problem was that my recipe files were taken from sstate directories, even when they were previously cleaned with bitbake -c clean. If I use -c cleansstate instead, all is ok .

AFAIK the task signatures will incorporate the values of all of the things your bbappend is setting, so this doesn't really account for the behaviour you are describing. Can you reproduce the issue?

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre